Metric Results

[ summary] [ packages] [ cycles] [ explanations]

The following document contains the results of a JDependmetric analysis. The various metrics are defined at the bottom of this document.

Summary

[ summary] [ packages] [ cycles] [ explanations]

Package TC AC CC AC EC A I D
olr 202315083%17%
olr.content 30316086%14%
olr.om 4420245120.4571%16%
olr.om.map 10010040100%0%
olr.presentation 692670290.03100%3%
olr.rdf 1165880.5550%5%
olr.rdf.util 211420.533%17%
olr.relations 10123060%40%
olr.samples 505070100%0%
olr.statementpool 835590.3864%2%
olr.toolbar 321360.6767%33%
olr.viewer 12111360.0867%25%
olr.vrp 20218089%11%

Packages

[ summary] [ packages] [ cycles] [ explanations]

olr.content

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
160%86%14%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

olr.om.map

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
040%100%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None None

olr.presentation

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
0293%100%3%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

olr.rdf.util

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
4250%33%17%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

olr.relations

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
230%60%40%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

olr.samples

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
070%100%0%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None None

olr.toolbar

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
3667%67%33%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages

olr.vrp

Afferent CouplingsEfferent CouplingsAbstractnessInstabilityDistance
180%89%11%
Abstract ClassesConcrete ClassesUsed by PackagesUses Packages
None

Cycles

[ summary] [ packages] [ cycles] [ explanations]

PackageCyclic Dependencies
olr
  • olr.toolbar
  • olr.viewer
  • olr
olr.content
  • olr.toolbar
  • olr.viewer
  • olr
  • olr.toolbar
olr.presentation
  • olr
  • olr.toolbar
  • olr.viewer
  • olr
olr.samples
  • olr
  • olr.toolbar
  • olr.viewer
  • olr
olr.toolbar
  • olr.viewer
  • olr
  • olr.toolbar
olr.viewer
  • olr
  • olr.toolbar
  • olr.viewer

Explanations

[ summary] [ packages] [ cycles] [ explanations]

The following explanations are for quick reference and are lifted directly from the original JDepend documentation.

TermDescription
Number of ClassesThe number of concrete and abstract classes (and interfaces) in the package is an indicator of the extensibility of the package.
Afferent CouplingsThe number of other packages that depend upon classes within the package is an indicator of the package's responsibility.
Efferent CouplingsThe number of other packages that the classes in the package depend upon is an indicator of the package's independence.
AbstractnessThe ratio of the number of abstract classes (and interfaces) in the analyzed package to the total number of classes in the analyzed package. The range for this metric is 0 to 1, with A=0 indicating a completely concrete package and A=1 indicating a completely abstract package.
InstabilityThe ratio of efferent coupling (Ce) to total coupling (Ce / (Ce + Ca)). This metric is an indicator of the package's resilience to change. The range for this metric is 0 to 1, with I=0 indicating a completely stable package and I=1 indicating a completely instable package.
DistanceThe perpendicular distance of a package from the idealized line A + I = 1. This metric is an indicator of the package's balance between abstractness and stability. A package squarely on the main sequence is optimally balanced with respect to its abstractness and stability. Ideal packages are either completely abstract and stable (x=0, y=1) or completely concrete and instable (x=1, y=0). The range for this metric is 0 to 1, with D=0 indicating a package that is coincident with the main sequence and D=1 indicating a package that is as far from the main sequence as possible.
CyclesPackages participating in a package dependency cycle are in a deadly embrace with respect to reusability and their release cycle. Package dependency cycles can be easily identified by reviewing the textual reports of dependency cycles. Once these dependency cycles have been identified with JDepend, they can be broken by employing various object-oriented techniques.